…, support, role-based sidebar)

Implements ROADMAP Wave-1 docs items #1, #10, #30, #32.

#1 — Fix the 10-vs-100 DIG cost conflict (trust-critical). The canonical
ecosystem price is a flat 100 DIG per capsule (mint OR commit), matching
SYSTEM.md. Corrected the three places that wrongly said `commit` = 10 DIG:
  - onchain-anchoring.md: the Costs table + the "Cost and safety" bullets
  - command-reference.md: the on-chain banner + the `commit` row
Added a "why the price is flat" explainer (fixed-size capsule → uniform price)
and an "iterate for free, pay only to publish" callout.

#10 — Web-first, zero-cost quickstart. New docs/quickstart.md front door:
free draft/preview FIRST (no wallet), fund + publish (100 DIG) only at the
end; parallel CLI track (new/dev marked coming-soon, init/commit/deploy real).
Retitled the old CLI quickstart to "CLI tutorial" and cross-linked the two.

#30 — Support + error codes. New docs/support/: troubleshooting.md, faq.md,
consolidated error-codes.md (dig RPC -32xxx + CLI exit codes 0–16 from
digstore-cli/src/error.rs + DIGHub codes from hub apps/web/lib/errors.js:
API_CODE_MESSAGES + DIG_INSUFFICIENT/SLUG_TAKEN/WALLET_DECLINED/…), get-help.md.
Added "Get help" + Discord to the navbar and a Community section to the footer
(+ discord.svg icon).

#32 — Role-based sidebar + canonical glossary. sidebars.ts now groups docs into
tracks: Start here / Build dapps / Deploy & host / Support / Protocol (kept at
position 90, low-prominence). concepts.md remains the single canonical glossary,
aligned with SYSTEM.md; cross-linked from intro, quickstart, and support.

Maintained agent-friendly conventions (frontmatter keywords/tags + "## Related"
on every new/edited page); regenerated static/knowledge-graph.json via the
prebuild script (51 nodes, 367 edges) and updated static/llms.txt. Applied
ecosystem vocab (DIG not $DIG, DIGHub, ↗ for external links). `npm run build`
green (onBrokenLinks: throw); typecheck clean.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GjQgGAisBupqs7vpkmUhuN

… read certs (#10)

The peer-network spec already had the two RPC tiers (mTLS peer/control vs
anonymous public-read) but treated rpc.dig.net as purely the anonymous
front. Node-class clients (digstore CLI, dig-sdk, any DIG-identity-key
holder) must never downgrade to that anonymous path, even at the public
gateway, per the client->node connection order contract.

- New peer-network.md §0a: rpc.dig.net is dual-mode — an mTLS front
  (CERT_REQUIRED) for node-class-client identity certs, reached at all
  three ladder tiers (dig.local/localhost/rpc.dig.net), alongside the
  existing plain-HTTPS+CORS front for browsers.
- Ephemeral self-signed client certificate flow: an anonymous reader may
  use the mTLS front for channel-bound request integrity without any
  persisted identity or reputation, binding a signed request to its TLS
  session.
- Design-status note: implementations gate on the gateway mTLS endpoint's
  existence and must not hard-break before it is deployed.
- Cross-link the dual-mode note into dig-rpc.md's public-read-tier tip and
  add a Related link + conformance/tier-map notes in peer-network.md.

Minor bump (additive normative spec content, no removed/renumbered
sections).

Co-Authored-By: Claude <noreply@anthropic.com>

…, support, role-based sidebar)

Implements ROADMAP Wave-1 docs items #1, #10, #30, #32.

#1 — Fix the 10-vs-100 DIG cost conflict (trust-critical). The canonical
ecosystem price is a flat 100 DIG per capsule (mint OR commit), matching
SYSTEM.md. Corrected the three places that wrongly said `commit` = 10 DIG:
  - onchain-anchoring.md: the Costs table + the "Cost and safety" bullets
  - command-reference.md: the on-chain banner + the `commit` row
Added a "why the price is flat" explainer (fixed-size capsule → uniform price)
and an "iterate for free, pay only to publish" callout.

#10 — Web-first, zero-cost quickstart. New docs/quickstart.md front door:
free draft/preview FIRST (no wallet), fund + publish (100 DIG) only at the
end; parallel CLI track (new/dev marked coming-soon, init/commit/deploy real).
Retitled the old CLI quickstart to "CLI tutorial" and cross-linked the two.

#30 — Support + error codes. New docs/support/: troubleshooting.md, faq.md,
consolidated error-codes.md (dig RPC -32xxx + CLI exit codes 0–16 from
digstore-cli/src/error.rs + DIGHub codes from hub apps/web/lib/errors.js:
API_CODE_MESSAGES + DIG_INSUFFICIENT/SLUG_TAKEN/WALLET_DECLINED/…), get-help.md.
Added "Get help" + Discord to the navbar and a Community section to the footer
(+ discord.svg icon).

#32 — Role-based sidebar + canonical glossary. sidebars.ts now groups docs into
tracks: Start here / Build dapps / Deploy & host / Support / Protocol (kept at
position 90, low-prominence). concepts.md remains the single canonical glossary,
aligned with SYSTEM.md; cross-linked from intro, quickstart, and support.

Maintained agent-friendly conventions (frontmatter keywords/tags + "## Related"
on every new/edited page); regenerated static/knowledge-graph.json via the
prebuild script (51 nodes, 367 edges) and updated static/llms.txt. Applied
ecosystem vocab (DIG not $DIG, DIGHub, ↗ for external links). `npm run build`
green (onBrokenLinks: throw); typecheck clean.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GjQgGAisBupqs7vpkmUhuN

… read certs (#10)

The peer-network spec already had the two RPC tiers (mTLS peer/control vs
anonymous public-read) but treated rpc.dig.net as purely the anonymous
front. Node-class clients (digstore CLI, dig-sdk, any DIG-identity-key
holder) must never downgrade to that anonymous path, even at the public
gateway, per the client->node connection order contract.

- New peer-network.md §0a: rpc.dig.net is dual-mode — an mTLS front
  (CERT_REQUIRED) for node-class-client identity certs, reached at all
  three ladder tiers (dig.local/localhost/rpc.dig.net), alongside the
  existing plain-HTTPS+CORS front for browsers.
- Ephemeral self-signed client certificate flow: an anonymous reader may
  use the mTLS front for channel-bound request integrity without any
  persisted identity or reputation, binding a signed request to its TLS
  session.
- Design-status note: implementations gate on the gateway mTLS endpoint's
  existence and must not hard-break before it is deployed.
- Cross-link the dual-mode note into dig-rpc.md's public-read-tier tip and
  add a Related link + conformance/tier-map notes in peer-network.md.

Minor bump (additive normative spec content, no removed/renumbered
sections).

Co-Authored-By: Claude <noreply@anthropic.com>